TRT-2350: Include additional OTE metadata in JUnit results #30431
Conversation
|
@stbenjam: This pull request references TRT-2350 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/test e2e-aws-ovn |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
openshift-ci
bot
added
the
do-not-merge/work-in-progress
stbenjam
force-pushed
the
ote-metadata-junit
branch
2 times, most recently
from
247aa01 to
fd4fb09
Compare
|
/test e2e-aws-ovn |
|
@neisw Updated to include additional info: <testcase
name="[Jira:config-operator][sig-api-machinery] sanity test should always pass [Suite:openshift/cluster-config-operator/conformance/parallel]"
time="0"
start-time="2025-11-12T20:06:48Z"
end-time="2025-11-12T20:06:48Z"
lifecycle="blocking"
source-image="cluster-config-operator"
source-binary="cluster-config-operator-tests-ext"
source-commit="347bebcc1"
/> |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
Extend JUnit test case schema with OpenShift Test Extensions (OTE) metadata attributes. Metadata fields added: - Lifecycle classification (blocking/informing) - Test execution timestamps (start-time, end-time) - Source tracking (source-image, source-binary, source-url, source-commit) The source fields allow tracking which container image, binary, repository, and commit produced each test result, enabling better traceability and debugging of test failures across different builds.
stbenjam
force-pushed
the
ote-metadata-junit
branch
from
fd4fb09 to
93a44f3
Compare
|
@stbenjam: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
3 participants
This allows us to add additional important information into the JUnit BigQuery table for use in Component Readness, or AI tools for analysis (e.g. correlating test failures with intervals).